Predictive recommendation system using tiered feature data

ABSTRACT

In general, embodiments of the present invention provide systems, methods and computer readable media for a predictive recommendation system using predictive models derived from tiered feature data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent application Ser. No. 14/814,154, titled “PREDICTIVE RECOMMENDATION SYSTEM USING TIERED FEATURE DATA,” filed Jul. 30, 2015, which claims the benefit of U.S. Provisional Application No. 62/031,071, entitled “PREDICTIVE RECOMMENDATION SYSTEM USING TIERED FEATURE DATA,” and filed Jul. 30, 2014, the contents of which are hereby incorporated herein by reference in their entirety.

BACKGROUND

Current methods for recommending device rendered objects to network asset requester devices exhibit a plurality of problems that make current systems insufficient, ineffective and/or the like. Through applied effort, ingenuity, and innovation, solutions to improve such methods have been realized and are described in connection with embodiments of the present invention.

SUMMARY

The capability to recommend promotions for purchase that are most relevant to each consumer is important for a promotion and marketing service. In some embodiments, a relevance system is used to select promotions to be recommended to a consumer (i.e., the available promotions that are most relevant to the consumer) based on using stored data representing attributes of promotions and/or the consumer, and is performed by executing a workflow that specifies a sequence of filtering rules and/or algorithms to be applied in selecting the relevant promotions.

In some examples, the digitalization of promotion and marketing has introduced specific problems not present in prior art promotion or marketing services found in print or broadcast media. In particular, advertisement space or time was generally constrained by the size of the print media or the length of the broadcast media. No such constraints are present in digital or online promotion and marketing. As such, a promotion and marketing service may have thousands or millions of different promotions, with only a subset of the promotions being currently viewable to the user.

As such, and according to some example embodiments, the systems and methods described herein are therefore configured to rank promotions selected for recommendation to consumers based on predictions of promotion performance and consumer behavior. The top-ranked promotions may be featured in a presentation to the consumer.

In some embodiments, each of a set of available promotions to be recommended to a particular consumer can be sorted and/or ranked according to a probability that the consumer's behavior in response to the promotion will match a ranking target (e.g., conversion rate, gross revenue). In some embodiments, promotions available to a consumer are ranked based on a relevance model derived from one or more data sources representing attributes of promotions and consumer behavior. Using the model, each promotion is associated with a relevance score that represents the probability that the consumer's behavior with respect to the promotion will approach the ranking target while the consumer interacts with an impression containing content describing the promotion. In some embodiments, the set of promotions selected for recommendation to a consumer can be sorted and/or ranked based on their respective associated relevance scores.

In embodiments, the relevance model may be a predictive function. In some embodiments, the predictive function may be a trainable function that is developed using machine learning. In some embodiments, the predictive function may be generated offline using supervised learning in a set of modeling stages in which the function is adapted based on training data sets of features that are extracted from a set of data sources (e.g., log data, promotion and user attribute data). In some embodiments, the set of data sources includes contextual data sources. In embodiments, examples of contextual data sources for mobile consumers may include user locations (prior, current, or potential) and their associated categories of interest; prior promotion interest level shown by the consumer; and prior promotion subcategory interest level.

In some embodiments, a feature set is aggregated to produce feature vectors to be used as input for predictive functions. In embodiments, a feature vector may include one or more combined features that each are derived from integrating historical behavior data collected from a sample of consumers and recently collected behavior data (Dynamic Deal Optimization (DDO) data). In some embodiments, a combined promotion performance feature value is a score that is calculated using a single data source in which historical performance data and DDO performance data have been integrated. This feature extraction method increases both efficiency and accuracy over alternative methods of calculating the combined performance score by combining separately calculated historical and DDO scores. In embodiments, DDO data may be aggregated at increasing levels of granularity (i.e., tiered) to ensure that creating an integrated data source representing a particular promotion does not have to depend on data collected at the promotion permalink level.

The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 illustrates an example system that can be configured to implement the relevance ranking of promotions that are available from a promotion and marketing service and are to be recommended to a particular consumer in accordance with some embodiments discussed herein;

FIG. 2 is a flow diagram of an example method for generating and ranking a set of promotions to be recommended to a consumer in accordance with some embodiments discussed herein;

FIG. 3 is a diagram of an exemplary overview process for generating a relevance model derived from contextual data sources and, based on the model, calculating a contextual relevance score for each of a set of available promotions to a mobile consumer during a workflow in accordance with some embodiments discussed herein;

FIG. 4 is an illustration of an exemplary process for generating a predictive relevance model that will be used in a workflow calculating a contextual relevance score in accordance with some embodiments discussed herein;

FIG. 5 is a flow diagram of an exemplary process for generating historical feature data used in a predictive relevance model that is determined based on a predicted gender type associated with first name data received in accordance with some embodiments discussed herein;

FIG. 6 illustrates a tiered logic flow for aggregating DDO data to use in a data source that integrates DDO and historical data in accordance with some embodiments discussed herein; and

FIG. 7 illustrates a schematic block diagram of circuitry that can be included in a computing device, such as a recommendation engine, in accordance with some embodiments discussed herein.

DETAILED DESCRIPTION

The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, this invention may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.

As described herein, system components can be communicatively coupled to one or more of each other. Though the components are described as being separate or distinct, two or more of the components may be combined into a single process or routine. The component functional descriptions provided herein including separation of responsibility for distinct functions is by way of example. Other groupings or other divisions of functional responsibilities can be made as necessary or in accordance with design preferences.

As used herein, the terms “data,” “content,” “information” and similar terms may be used interchangeably to refer to data capable of being captured, transmitted, received, displayed and/or stored in accordance with various example embodiments. Further, where a computing device is described herein to receive data from another computing device, the data may be received directly from the another computing device or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, and/or the like. Similarly, where a computing device is described herein to send data to another computing device, the data may be sent directly to the another computing device or may be sent indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, and/or the like.

As used herein, the term “promotion and marketing service” refers to a service that is accessible via one or more computing devices and is operable to provide example device rendered object transaction services (e.g., promotion and/or marketing services) on behalf of one or more providers that are offering one or more instruments that are redeemable for goods, services, experiences and/or the like. The promotion and marketing service is further configured to illustrate or otherwise inform one or more consumers of the availability of one or more instruments in the form of one or more impressions (i.e., device rendered objects). In some examples, the promotion and marketing service may also take the form of a redemption authority, a payment processor, a rewards provider, an entity in a financial network, a promoter, an agent and/or the like. As such, the service is, in some example embodiments, configured to present one or more promotions via one or more impressions, accept payments for promotions from consumers, issue instruments upon acceptance of an offer, participate in redemption, generate rewards, provide a point of sale device or service, issue payments to providers and/or or otherwise participate in the exchange of goods, services or experiences for currency, value and/or the like.

As used herein, the term “network asset provider” may be used to refer to a network actor capable of providing a network asset to another computing device. A network asset may be a set of instructions that, when executed by a computing device, renders an instrument redeemable for a network asset. An example of a network asset provider may be a provider or a merchant.

As used herein, the term “provider” refers to a merchant, business owner, consigner, shopkeeper, tradesperson, vender, operator, entrepreneur, agent, dealer, organization or the like that is in the business of a providing a good, service or experience to a consumer, facilitating the provision of a good, service or experience to a consumer and/or otherwise operating in the stream of commerce. For example, a provider may be in the form of a running company that sells attire that is generally used by a person who runs or participates in athletic activities.

As used herein, the term “network asset requester” may be used to refer to a requester for network assets that may be purchased, consumed, or redeemed by the network asset requester. Examples of a network asset requester may include a consumer.

As used herein, the term “consumer” should be understood to refer to a recipient of goods, services, promotions, media, or the like provided by the promotion and marketing service and/or a merchant. Consumers may include, without limitation, individuals, groups of individuals, corporations, other merchants, and the like.

As used herein, the terms “network asset” and “device rendered object” may be used interchangeably to mean an electronic representation of or an instrument redeemable for a digital promotion or marketing service provided by one or more providers that are offering one or more instruments that are redeemable for goods, services, experiences and/or the like. In some examples, the system may take the form of a server enabling transactions related to redemption of promotions associated with device rendered objects, processing of financial transactions associated with device rendered objects, and/or the like. As such, the system is, in some example embodiments, configured to present one or more device rendered objects that display promotions via one or more impressions, accept payments for promotions from consumers, issue instruments upon acceptance of an offer or a promotion, participate in redemption, generate rewards, provide a point of sale device or service, issue payments to providers and/or otherwise participate in the exchange of goods, services or experiences for currency, value and/or the like. The system is also, in some example embodiments, configured to enabling object parameter analysis, whereby parameters associated with device rendered objects can be optimally selected, including parameter analytics, and the like. Examples of device rendered objects or network assets may include promotions or deals. The terms device rendered objects and network assets are used interchangeably with promotion.

As used herein, the terms “promotion,” “offer,” “deal” and similar terms refer to any type of offered, presented or otherwise indicated reward, discount, coupon, credit, incentive, discount, media or the like that is indicative of a promotional value or the like that upon purchase or acceptance results in the issuance of an instrument that may be used toward at least a portion of the purchase of particular goods, services and/or experiences defined by the promotion. An example promotion, using the aforementioned running company as the example provider, is $25 for $50 toward running shoes. In some examples, the promotion defines an accepted value (e.g., a cost to purchase the promotion), a promotional value (e.g., the value of the resultant instrument beyond the accepted value), a residual value (e.g., the value upon return or upon expiry of one or more redemption parameters), one or more redemptions parameters and/or the like. For example, and using the running company promotion as an example, the accepted value is $25 and the promotional value is $50. In this example, the residual value may be equal to the accepted value.

As used herein, the term “instrument” refers to any type of gift card, tender, electronic certificate, medium of exchange, voucher, or the like that embodies the terms of the promotion from which the instrument resulted and may be used toward at least a portion of the purchase, acquisition, procurement, consumption or the like of goods, services and/or experiences. In some examples, the instrument may take the form of tender that has a given value that is exchangeable for goods, services and/or experiences and/or a reduction in a purchase price of a particular good, service or experience. In some examples, the instrument may have multiple values, such as accepted value, a promotional value and/or a residual value. For example, using the aforementioned running company as the example provider, an electronic indication in a mobile application that shows $50 of value to spend at the running company. In some examples, the accepted value of the instrument is defined by the value exchanged for the instrument. In some examples, the promotional value is defined by the promotion from which the instrument resulted and is the value of the instrument beyond the accepted value. In some examples, the residual value is the value after redemption, the value after the expiry or other violation of a redemption parameter, the return or exchange value of the instrument and/or the like.

As used herein, the term “impression” refers to a communication, a display, or other perceived indication, such as a flyer, print media, e-mail, text message, application alert, mobile applications, other type of electronic interface or distribution channel and/or the like, of one or more promotions. For example, and using the aforementioned running company as the example provider, an e-mail communication sent to consumers that indicates the availability of a $25 for $50 toward running shoes promotion.

As used herein, the terms “user device,” “consumer device,” “client device,” “network asset requester” and similar terms refer to computer hardware and/or software that is configured to access a service (e.g., a promotion and marketing service) made available by a server. The server is often (but not always) embodied by another computer system, in which case the client device accesses the service by way of a network. Client devices may include, without limitation, smart phones, tablet computers, laptop computers, wearables, personal computers, enterprise computers, and the like.

As used herein, the terms “user profile, “user profile,” “user account,” and “user account details” refer to information associated with a user, including, for example, a user identifier, gender data identifying a gender type (e.g., a male type, a female type, or an unknown type) that is provided by an existing user associated with a user profile, predicted gender data identifying a predicted gender type (e.g., a male type, a female type, or an unknown type) determined based on a gender prediction outcome of the system disclosed herein, user location data identifying a user's locations (prior, current, or potential), categories of interest associated with a user, prior promotion interest level associated with a user, prior promotion subcategory interest level, an email address, name data identifying a real name (e.g., John Doe) and a username (e.g., jdoe) of a user associated with a user device, first name data identifying a first name (e.g., John) of a user associated with a user profile, a password, a time zone, a status, and the like.

As used herein, the term “first name data” refers to data that is stored to a user profile identifying a first name of a user associated with the user profile. First name data may be input by a user in response to a service a device prompts to the user in a graphic user interface to enter a given name, a legal name, and/or a forename.

As used herein, the term “gender types” refers to a set of gender categorization information (e.g., a male type, a female type, or an unknown type) related to gender data that is provided by existing users and associated with existing user profiles. As used herein, the term “predicted gender types” refers to a set of gender categorization information (e.g., a male type, a female type, or an unknown type) related to predicted gender data that is determined based on a gender prediction outcome of the system disclosed herein. In one embodiment, a gender type or a predicted gender type may be an indicia, a text, a binary or the like representing the set of gender categorization information (e.g., a male type, a female type, or an unknown type) that is related to gender data or predicted gender data associated with a specific user profile. In such an embodiment, a gender type or a predicted gender type may refer that the user profile is categorized as a male type, a female type, or an unknown type.

As used herein, the term “known gender data” refers to a set of gender data aggregated from user profiles associated with common first name data. The known gender data is aggregated and used for gender prediction associated with each first name data. In one embodiment, the known gender data may include aggregated gender data identifying gender types (e.g., a male type, a female type, or an unknown type) that are provided by existing users associated with existing user profiles with common first name data. In another embodiment, the known gender data may include both aggregated gender data identifying gender types (e.g., a male type, a female type, or an unknown type) that are provided by existing users associated with existing user profiles and aggregated predicted gender data identifying predicted gender types (e.g., a male type, a female type, or an unknown type) determined based on a gender prediction outcome of the system disclosed herein.

As used herein, the term “gender ratio” refers to a ratio correlated to a gender type associated with first name data that is collected from user profiles associated with known gender data. A gender ratio may be calculated based on first name data in view of gender types collected from user profiles associated with the known gender data. For any selected first name represented by first name data, the gender ratio represents the ratio of a population of user profiles correlated to a selected gender type associated with the known gender data divided by the total population of user profiles correlated to all users associated with the known gender data.

For example, in a case where the total existing user profiles associated with known gender data that is associated with a first name—Alex—has a population of 100, in which 80 out of 100 are categorized as male types based on gender types or predicted gender types and 20 out of 100 are categorized as female types based on gender types or predicted gender types. In such a case, a gender ratio correlated to the male type associated with Alex is 0.80, while a gender ratio correlated to the female type associated with Alex is 0.20.

In the Alex example described above, the gender ratios correlated to respective gender types may serve as probabilities showing confidence of a gender prediction outcome. In the Alex example, the gender ratio correlated to the male type associated with Alex is 0.80, which shows a probability of 80% that a user associated a user profile with Alex as first name is a male type. Similarly, the gender ratio correlated to the female type associated with Alex is 0.20, which shows a probability of 20% that a user associated a user profile with Alex as first name is a female type.

In another example, gender ratios may serve as probabilities and confidence intervals for the probabilities may be generated and used for determining a confidence of a gender prediction outcome. A confidence interval for a probability may be a type of interval estimate that is computed from known gender data correlated to a gender ratio. In such an example, the lower bound of the confidence interval is compared with a threshold ratio defined below to determine a gender prediction outcome confidence. When the lower bound is larger than or equal to the threshold ratio, it shows a high gender prediction outcome confidence. Thus, the gender data associated with the user profile may be predicted according to the gender ratio associated with the lower bound. When the lower bound is smaller than the threshold ratio, it shows a low gender prediction outcome confidence. Thus, gender type related to gender data associated with the user profile may remain as an unknown type.

As used herein, the term “threshold ratio” refers to a value defined for determining whether a predicted gender type should be associated with a selected user profile. For example, a threshold ratio may be defined as 0.85. In such an example, when a gender ratio is calculated to be 0.90 (which is larger than the threshold ratio 0.85 and shows a high gender prediction outcome confidence), the system disclosed herein would store to a user profile a predicted gender type according to a gender type associated with the gender ratio. When a gender ratio is calculated to be 0.20 (which is smaller than the threshold ratio 0.85 and shows a low gender prediction outcome confidence), the system disclosed herein would store to a user profile a predicted gender type as an unknown type.

In some embodiments, a predicted gender type (e.g., a male type, a female type, or an unknown type) is used in a predictive recommendation system, which is incorporated in the system disclosed herein, to generate a combined feature representing a promotion to be recommended to a user for purchase. For example, a predicted gender type may refer to a male type, a female type, or an unknown type, wherein the predicted gender type is determined based on gender ratios associated with the first name data. In such an example, the predicted gender type of a selected user profile is determined based on first name data received from a user device and gender ratios associated with the first name data. The gender ratios are calculated based on known gender data collected from existing user profiles associated with the first name data in view of respective gender types. In such an example, the predicted gender type is determined by comparing each of the gender ratios with a threshold ratio. In an instance in which a gender ratio correlated to a gender type associated with the first name is larger than or equal to the threshold ratio, the predicted gender type is determined to be the gender type and stored to the selected user profile. In an instance in which all of the gender ratios correlated to a gender type associated with the first name is smaller than the threshold ratio, the predicted gender type is determined to be an unknown type and stored to the predicted user profile.

In some embodiments, known pairs of first name data and associated gender types are used to train a machine learning model. In such embodiments, subsequent to the machine learning model having been trained, the machine learning model may be fed a user's first name data and may output a predicted gender type for the received first name data.

As used herein, the terms “permalink,” “permanent link” and similar terms refer to a web address, such as a Uniform Resource Locator (URL), wherein the web address may refer to a web resource that specifies its location on a computer network and a mechanism for retrieving information from the web resource.

As used herein, the term “DDO feature data” refers to information or data correlated to DDO data (Dynamic Deal Optimization data; DDO data hereinafter). DDO data may include historical behavior data collected from a sample of consumer devices and recently collected behavior data (e.g., a data sample that trails over the past 90 days), wherein the DDO data may show performance associated with a permalink related to a past deal/promotion, based on mapping an individual deal/promotion/offer's performance data associated with the permalink to all user devices similar to the given user device. DDO feature data may be a subset of information or data collected from the DDO data that is associated with a particular subset of past deal deal/promotion/offer's performance at the permalink level. A model, such as a model relating to DDO, is further described with reference to U.S. patent application Ser. No. 13/839,360 entitled “Dynamic Promotion Analytics,” filed on Mar. 15, 2013, and which is incorporated by reference herein in its entirety.

In one embodiment, DDO feature data may be aggregated at increasing levels of granularity (i.e., “tiered DDO feature data” used hereinafter) to ensure that an integrated data source representing a particular subset of past deal deal/promotion/offer may be created and does not have to depend on data collected at the promotion permalink level.

As used herein, the term “historical feature data” refers to data associated with a user device that shows information including detected historical trends or a predicted gender type related to the user device. For example, the historical feature data may be data collected based on a user's past clicks, via a user device, on a category of deal/promotion/offer permalinks that show a historical trend regarding the user's interest. The historical feature data may be stored in one or more historical databases.

It will be appreciated that network assets, device rendered objects, network asset providers, network asset requesters, and the like, as described herein, may have associated therewith one or more attributes.

It should be understood that each of the attributes discussed in this application, may be in some embodiments, may be a primary or a secondary attribute. A list of exemplary attributes is provided below. It will be appreciated that network asset group location, group network asset type, network asset location, and asset type can be considered attributes. It will also be appreciated that a network asset provider record and a network asset provider group may comprise additional attributes. Further, network asset search requests and network asset requests may be associated with one or more attributes.

In some implementations, one attribute may represent category data, specifically beauty, wellness and healthcare. To determine a normalized value of the one attribute, an algorithm may be executed on associated raw data related to a transaction. For example, if the category data associated with a promotion transaction is “beauty, wellness and healthcare,” the value of the one attribute is 1. If the category data associated with a transaction is not “beauty, wellness and healthcare,” the value of the one attribute is 0.

In some embodiments, a number of example attributes relate to category data and sub-category data. There is also a number of attributes related to location data. It should be understood that attribute data related to location and hyper location data may be generated in a similar fashion. For example, if the location data associated with a transaction is “Chicago,” the value of a corresponding attribute may be 1. If the category data associated with a transaction is not “Chicago,” the value of the corresponding attribute may be 0.

It should also be understood that transactions may have associated data indicating one or more categories, sub-categories, location, hyper-locations, prices or the like. For example, a transaction may be associated with a gym, and the gym may be associated with category data such as “beauty, wellness, and healthcare,” “Food and drink,” “Leisure Offers and Activities” and/or “Services.” A gym may also have more than one location, and may be able to provide promotions in a variety of price ranges and time frames.

Example attribute data can also be associated with review websites such as Yelp®, Google®, Yahoo®, City Search®, Trip Advisor®. It should be understood that any review website could have associated attribute data, such as for example Zagat®, Bing® or the like. It should also be understood that attribute data associated with reviews related to one or more categories may be generated. For example, a website may provide reviews related to a provider's food, service, décor, price or the like. Attribute data may be generated related to each of one or more categories, such as a provider's food, service, décor, price, or the like.

It should also be understood that a location, hyper-location, category or sub-category may affect data available for the provider of a transaction. For example, promotion transactions purchased from providers from different locations (e.g., different countries, states, neighborhoods or the like) may be associated with different attribute data. For example, different countries have different credit reporting rules and agencies. Thus, a system may utilize a first combination of attributes for a transaction from a provider in a first location, hyper-location, category or sub-category and a second combination of attributes for a transaction from provider in a second location, hyper-location, category or sub-category.

In one implementation, other attribute data may be used. For example, attribute “bad month” may relate to identifying transactions having attributes associated with network time intervals (e.g., booking months) where prior transactions have involved products, services, and/or other offerings in one or more categories categorized as having high termination transaction rates based on prior performance data. The feature may be normalized such that if the sub-category of the promotion transaction is associated with high return rates, the attribute is 1, else the attribute is 0. Other example attributes are “bad market,” which may be normalized such that if the transaction has an attribute associated with GPS coordinates that indicate a significant distance requiring travel to a location and/or hyper local region associated with high return rates, the attribute is 1, else the attribute is 0. Another example feature is “average price for sub-category.”

Similar attributes may be clustered, grouped, or aggregated. For example, attributes associated with locations or location based attributes may be grouped under header attribute “location.” For example, a division attributes specifying a division where the promotion is offered and an attribute specifying a distance from a center of a city where a promotion is offered may be clustered under the location header attribute. Similarly, attributes associated with “past performance,” “category & service,” “completion,” “maximum capacity,” “hero score,” “review data” may each also be clustered and/or grouped under header attributes. For example, with respect to promotion transaction associated with a merchant providing a service, attributes specifying past performance data can be for (1) the same merchant and the same service, (2) only the same merchant, (3) only the same service may be clustered under attribute header “past performance.”

Table A shows example attributes.

TABLE A Type Features Location division, distance to city, etc. past performance same merchant & service, same service, same merchant, etc. category & service service header, primary deal service, etc. booking month holiday, pre-holiday, etc. maximum capacity units_avail, etc. hero score predicted 30 day bookings, predicted 60 day bookings, etc. review data yelp_n_review, yelp_rating, yelp_avil, google_n_review, facebook_fans, etc.

The clustered or the non-clustered attributes may be used to train a machine learning model. It should be understood that the selection of attributes or clusters of attributes for training machine learning models or for promotion termination prediction processes can greatly affect the respective performance. In some implementations, attributes and/or clusters of attributes are selected based on statistical analysis. In some implementations, selection of the most significant attributes is based on one or more different attribute selection approaches. These approaches may be (1) forward selection, which is starting with the most significant attributes and incrementally adding a next significant attribute until the model is stable; (2) backward elimination, which starts with all the attributes and exclude the non-significant attributes one by one until the model is stable; (3) a combination of forward selection and backward elimination; and (4) checking the significance of the attribute by statistical model (regression). In one embodiment, each attribute selection approach may give a subset of significant attributes. The attributes that are not shown to be significant by one or more of the attribute selection approaches may be excluded from the model.

FIG. 1 illustrates an example system 100 that can be configured to implement the relevance ranking of promotions that are available from a promotion and marketing service and are to be recommended to a particular consumer (i.e., “user”). System 100 comprises a relevance service 110 that returns a set of available promotions 112 that are ranked for relevance to a consumer in response to receiving a request 102 for available promotions on behalf of the consumer; a user profiles repository 120 in which data representing profile attributes of consumers are stored; a promotions repository 130 in which data representing attributes of promotions are stored; a user activation states repository 140 in which data representing consumer activation states respectively associated with consumers are stored; and a user behavioral data repository 150 in which historical data representing the respective consumer behavior of consumers are stored. The relevance service 110 includes a recommendation engine 115 that is configured to select available promotions to be recommended to a particular consumer.

In some embodiments, recommendation engine 115 generates a set of available promotions that are most relevant to a consumer in response to receiving consumer identification data representing the consumer. In some embodiments, generating the set of available promotions includes selecting the promotions using stored data representing attributes of promotions and/or the consumer, and is performed by executing a workflow that specifies a sequence of filtering rules and/or algorithms to be applied in selecting the relevant promotions. A workflow may include ranking the selected promotions for relevance to the consumer and then ordering the selected promotions based on their respective rankings. In some embodiments, the most highly ranked promotions may be presented to the consumer as featured recommended promotions.

FIG. 2 is a flow diagram of an example method 200 for generating and ranking a set of promotions to be recommended to a consumer. Systems and methods for generating and ranking a set of promotions to be recommended to a consumer are described, for example, in U.S. patent application Ser. No. 14/231,222 entitled “Predictive Recommendation System Using Contextual Relevance,” filed on Mar. 31, 2014, and which is incorporated herein in its entirety. For convenience, the method 200 will be described with respect to a system, including one or more computing devices, that performs the method 200. Specifically, the method 200 will be described with respect to its implementation by recommendation engine 115 in system 100.

In embodiments, the system receives 205 input data representing a request from a consumer. The input data can include consumer identification data. In some embodiments, for example, the consumer identification data may include a unique consumer identifier (e.g., a login identifier that is provided by a consumer when the consumer interacts with the content) and/or at least one consumer-associated bcookie, which is a unique identifier of a device (e.g., a mobile phone, a tablet, or a personal computer) and/or a mobile application or browser from which the consumer accesses the content. Identifying a consumer through associated bcookies ensures that a wider variety of behavioral data may be collected from the consumer since not all types of consumer access to content require the consumer to first provide a unique identifier.

In embodiments, the system receives 210 user profile describing attributes of the consumer. In some embodiments, the user profile may include gender data identifying a gender type (e.g., a male type, a female type, or an unknown type) that is provided by an existing user associated with a user profile, predicted gender data identifying a predicted gender type (e.g., a male type, a female type, or an unknown type) determined based on a gender prediction outcome of the system disclosed herein, or first name data identifying a first name (e.g., John) of a user associated with a user profile. In some embodiments, the user profile may include historical data representing the consumer's previous consumer behavior. In some embodiments, the behavioral data that is collected from a particular consumer can be associated with that consumer's identification data so that a collection of multiple instances of behavior from a single consumer may be stored as history data in a consumer behavioral data repository 150. Examples of collected consumer behavioral data include instances of consumer engagement with published content (e.g., instances in which a consumer opens a mobile application, clicks on and/or opens an email, or visits a website), and consumer activation state (e.g., instances in which a consumer makes a promotion purchase).

In embodiments, the system receives 215 promotion data describing attributes of a set of promotions that currently are available to the consumer. In some embodiments, the set of available promotions are selected in response to a search query that is executed against promotions data, stored in a promotions repository 130, describing attributes of promotions in a promotions inventory. In some embodiments, the promotions repository 150 may be a implemented within a parallel distributed search platform (e.g., open-source “Elasticsearch,” see http://www.elasticsearch.org/), and returning results from the search query may be implemented by sharding data including a set of promotion attributes as well as consumer attributes described in the received input data and/or the received user profile. Additionally and/or alternatively, in some embodiments, the set of promotions may be selected by executing a sequence of filtering rules and/or algorithms that are applied to one or a combination of the promotions data, the input data, and/or the user profile.

In embodiments, the system calculates 220 a contextual relevance score for each of the set of available promotions. In some embodiments, the system calculates the contextual relevance score for each available promotion using one or a combination of the input data, the promotion data, and the user profile and based on at least one relevance model derived from a set of contextual data sources. In embodiments, the contextual relevance score represents a predicted probability that the consumer will purchase the promotion if the promotion is included in the content of an impression distributed to the consumer.

In embodiments, the system ranks 225 the set of available promotions based on their respective contextual relevance scores using a relevance model. In some embodiments, each of a set of available promotions to be recommended to a particular consumer can be ranked, based on data representing the promotion's performance and the consumer's behavior, according to a probability that the consumer's behavior in response to the promotion will match a ranking target.

In some embodiments, each promotion is represented by a feature vector that includes feature data representing attributes of the promotion and attributes of the consumer. In some embodiments, the feature data elements of the feature vector are selected based on the ranking target. There is a variety of well-known types of predictive functions (e.g., clustering algorithms, classifiers, neural networks, ensemble of trees), and the implementation choice of predictive function is not critical to the invention.

FIG. 3 is a diagram of an exemplary overview process 300 for generating a relevance model derived from contextual data sources and, based on the model, calculating a contextual relevance score for each of a set of available promotions to a mobile consumer during a workflow. Contextual mobile relevance generally refers to mobile relevance based on the context (e.g., the where/when/how/who/why) within which a request for promotions on behalf of a consumer occurs. In embodiments, examples of contextual data sources for mobile consumers may include user locations (prior, current, or potential) and their associated categories of interest; prior promotion interest level shown by the consumer; and prior promotion subcategory interest level.

In some embodiments, the relevance model can be generated offline using supervised learning. In a typical supervised learning scenario, a predictive function that maps an input value to one of a set of predefined output values is adapted, in response to exposure to a training data set containing examples of inputs and their respective associated outputs, to perform a mapping that represents a particular predictive model. In some embodiments, the predictive function maps data representing the promotion's performance and the consumer's behavior to one of a set of probability classes, each class representing a different probability that the data matches a ranking target.

In some embodiments, the predictive function may be generated offline using machine learning in a set of modeling stages 320 in which the function is adapted (e.g., in stage 325) based on a set of features that are extracted (e.g., in stages 321, 322, and 323) from a set of data sources (e.g., log data, promotion and user attribute data). In some embodiments, the set of data sources includes contextual data sources.

FIG. 4 is an illustration of an exemplary process 400 for generating a predictive relevance model that will be used in a workflow calculating a contextual relevance score. Specifically, process 400 may be implemented in the modeling stages 320 and used in one or more of the workflow stages 340 of process 300.

In embodiments, the predictive model feature data source 410 includes methods for extracting feature data values from a set of data sources received during a set of data collection stages (e.g., stages 321, 322, and 323 in FIG. 3). In embodiments in which the predictive model represents a mobile consumer, the features can include attributes of the consumer (e.g., bcookie engagement/activation state, distance from cookie to promotion); attributes of the promotion (e.g., promotion category, promotion price); and consumer behavior of a particular consumer (e.g., # impressions of the promotion for the bcookie) and/or historical behavior data collected from a sample of consumers (e.g., clicks per impression of the promotion (all bcookies).

In some embodiments, a feature set is aggregated (e.g., stage 324) to produce feature vectors to be used as input for predictive functions. Each of the feature vectors has reduced dimensionality and optimally represents the model of the ranking target associated with the predictive function. For example, in some embodiments in which the type of predictive function is an ensemble of trees, a random forest algorithm is used to produce 10 tree ensembles with a maximum of 20 nodes per tree. The random forest algorithm generates a ranking target model as output, as well as calculates the relative importance of each of the features used in the model. Extracting feature data values is described, for example, in U.S. patent application Ser. No. 13/929,977 entitled “Predictive Recommendation System,” filed on Jun. 28, 2013, and which is incorporated herein in its entirety.

The generated predictive model (e.g., models 336 and 338 in FIG. 3) is represented by a predictive model definition file 430, which is generated by a predictive model builder 420. In embodiments, the predictive model 440, including the predictive model definition file 430 and predictive model feature data source 410, may be accessed by recommendation engine 115 for data feature extraction and calculation of a contextual relevance score during a runtime workflow stage 450 (e.g., scoring stage 344 in FIG. 3).

In embodiments, a feature vector may include one or more combined features that each are derived from integrating historical behavior data collected from a sample of consumers and recently collected behavior data (Dynamic Deal Optimization data; DDO data hereinafter) (e.g., a data sample that trails over the past 90 days). A model, such as a model relating to DDO, is further described with reference to U.S. patent application Ser. No. 13/839,360 entitled “Dynamic Promotion Analytics,” filed on Mar. 15, 2013, and which is incorporated herein in its entirety.

As previously described with reference to modeling stages 320, a predictive model (e.g., conversion model 336) is an odds model derived using a set of features that are extracted (e.g., in stages 321, 322, and 323) from a set of data sources. For example, a historical consumer behavior feature extracted for a particular promotion from a stored set of data may represent long term trends based on millions of impressions that have been collected over a period of years. Historical data trends tend to be at the promotion category or subcategory level of granularity. Typically, historical feature data is updated infrequently (e.g., once every two years), since any new data being collected will need to accumulate before it is likely to affect the statistical distribution of the stored data. A model, such as the odds model, is further described with reference to U.S. patent application Ser. No. 13/411,502 entitled “Relevance System for Consumer Deals,” filed on Mar. 2, 2012, and which is incorporated herein in its entirety.

In contrast, the DDO data are collected at the promotion level of granularity, and the data may represent dynamic shorter term trends that could affect the calculation of a promotion's contextual relevance score during a runtime workflow stage. For example, in embodiments, DDO data may reflect seasonal changes in consumer behavior (e.g., promotions for swimming lessons may be more in demand during summer, while promotions for goods may be more in demand during the Christmas season); global seasonal effects (e.g., the northern hemisphere has opposite seasons from the southern hemisphere); and/or cultural differences between consumers in different countries (e.g., French consumers tend to purchase more leisure activities than German consumers).

A predictive model based on combined features representing an integration of historical data and DDO data is a more accurate model, because it can generate its predictions based on long term trends and short term trends simultaneously. Such a model is a more general model that applies to a wider range of current data input, thus eliminating the need to either re-generate the model to capture short-term data fluctuations or to generate multiple models that each represent a particular type of trend (e.g., have a summer odds model and a winter odds model).

In some embodiments, a combined promotion performance feature value is a score that is calculated using a single data source in which historical performance data and DDO performance data have been integrated. This feature extraction method increases both efficiency and accuracy over alternative methods of calculating the combined performance score by combining separately calculated historical and DDO scores.

FIG. 5 is a flow diagram of an example method 500 for generating historical feature data used in a relevance model that is determined based on a predicted gender type associated with first name data received. For convenience, the method 500 will be described with respect to a system, including one or more computing devices, that performs the method 500. Specifically, the method 500 may be implemented in the modeling stage 320 in process 300.

In some embodiments, the system receives 505 a first name data from a user device. In one example, the first name data may be included in a user profile associated with a user device.

In some embodiments, the system retrieves 510 known gender data from one or more user profiles associated with the first name data from a memory 704, as described with reference to FIG. 7. In one example, the known gender data is a set of gender data collected from existing user profiles that include a gender type (e.g., a male type, a female type, or an unknown type) provided by user devices. In such an example, the known gender data is used in later calculation of gender ratios that are each correlated to respective gender types (e.g., a male type, a female type, and an unknown type) for training a machine learning model and/or determining a predicted gender type associated with the first name data.

In some embodiments, the system calculates 515 one or more gender ratios that are each correlated to respective gender types (e.g., a male type, a female type, and an unknown type) based on the known gender data retrieved from the one or more user profiles associated with the first name data. The calculation may be completed by a processor 702, as described with reference to FIG. 7.

In some embodiments, the system compares 520 each of the one or more gender ratios that are each correlated to the respective gender types with a threshold ratio. The comparison may be completed by a processor 702, as described with reference to FIG. 7.

In an instance in which a gender ratio is larger than or equal to a threshold ratio, the system determines 525 the predicted gender type to be a gender type correlated to the gender ratio. In an instance in which a gender ratio is smaller than a threshold ratio, the system determines 530 the predicted gender type to be an unknown type. The determination may be completed by a processor 702, as described with reference to FIG. 7.

In one example, the threshold ratio may be 0.85. In such an example, if a gender ratio calculated in step 515 is larger than or equal to 0.85, the system determines in step 525 that there is a high gender prediction outcome confidence. Accordingly, the system may determine the predicted gender type to be the gender type associated with the gender ratio with high confidence (i.e., larger than the preset threshold ratio). If a gender ratio calculated in step 515 is smaller than 0.85, the system determines in step 530 that there is a low gender prediction outcome confidence of. Accordingly, the system may determine the predicted gender type remains an unknown type since there is a low gender prediction outcome confidence (i.e., smaller than the preset threshold ratio).

In some embodiments, the system generates 535 historical feature data based on a predicted gender type associated with the first name data. The historical feature data and predicted gender type may be generated using machine learning techniques. For example, a predicted gender type may be generated based on gender ratios calculated in step 515, wherein the gender ratios are calculated based on known gender data collected from existing user profiles that include a gender type provided by existing users and are used to train a machine learning model incorporated in the system disclosed herein. More specifically, due to the dynamic features of the known gender data (i.e., aggregated gender data collected from existing user profiles that are dynamically changing according to user devices, such as new registrations of user devices may add new gender data to known gender data), the gender ratios calculated in step 515 may change their results dynamically and serve to train the machine learning model incorporated in the system disclosed herein. In the an example, the historical feature data correlated to a predicted gender type may also be generated based on the gender ratios used to train the machine learning model incorporated in the system disclosed herein.

FIG. 6 illustrates a tiered logic flow 600 for aggregating DDO data to use in a data source that integrates DDO and historical data. Since DDO data are collected from impressions at the promotion level (i.e., impression data associated with a particular promotion permalink), there may not be enough collected impression data to integrate with the larger historical data sample. For example, in some embodiments, a DDO sample size of ≥1 million impressions is necessary to blend with historical data before calculating a feature value (e.g., a promotion performance score). Although popular and/or featured deals may enable data to be collected from the requisite number of impressions during the DDO sample window, mid-level deals are not likely to generate that many impressions. Thus, in embodiments, DDO data may be aggregated at increasing levels of granularity (i.e., tiered) to ensure that creating an integrated data source representing a particular promotion does not have to depend on data collected at the promotion permalink level.

In embodiments, the system receives extracted DDO feature data from a promotion. The system first determines whether there have been enough impressions to satisfy a previously determined threshold quantity (e.g., ≥1 million impressions) represented in that data to use the data at the promotion permalink level. If not, the system determines whether there have been enough impressions to satisfy the threshold quantity for the group of promotions in the promotion's next tier (i.e., second level subcategory (subcat2). The system proceeds to the next tier group to increase the number of promotions to consider until the largest tier group of promotions is evaluated (e.g., promotion category). If the number of impressions generated from the category does not satisfy the threshold quantity, the system does not integrate the DDO data (i.e., uses a null default).

For example, a combined promotion performance feature value for a massage promotion need not require DDO data related to a specific massage promotion, but instead may represent integrated historical and DDO performance data collected for spas promotions (the massage promotion subcategory) or for wellness promotions (the massage promotion category).

In an exemplary, embodiment a promotion and marketing system, performing the steps of FIG. 5, may define a taxonomy that comprises multiple categories, sub-categories and/or promotions. The categories may be categories associated with the subject matter of the products, services or experiences provided by the promotions. For example, a promotion for a discounted gold necklace may have an associated category of “Jewelry” and sub-categories of “Jewelry—Necklace” and “Jewelry—Gold.”

In certain cases, an exemplary purchase category may indicate a subject matter or a functional classification of a commercial object, e.g., jewelry, pharmaceuticals, toiletries, cosmetics, home improvement, and the like. An exemplary sub-category may provide more granular indications of a subject matter or a functional classification of a commercial object, e.g., jewelry—men, pharmaceuticals—skin, home improvement—kitchen. Even more granular sub-categories may also be provided.

In certain cases, a category or sub-category may broadly indicate a classification of any feature of a commercial object. Exemplary categories or sub-categories may describe, for example, a subject matter associated with the commercial object (e.g., category “outdoorsy” may describe an outdoor equipment), a genre of a product (e.g., category “Italian food” or “sushi” may describe a type of food sold), a feature or component of a commercial object (e.g., category “spicy” may describe food that is spicy, categories “vegetarian,” “fatty” and “gluten-free”), and the like.

In certain cases, a category or sub-category may indicate a contextual description describing a contextual feature or attribute of a commercial object. Exemplary contextual categories may describe, for example, a setting (e.g., category “romantic” may describe a restaurant as having a romantic setting), and the like.

In certain cases, a category or sub-category may indicate a quality associated with a commercial entity or object. Exemplary quality attribute descriptors may describe, for example, durability (e.g., category “rugged” may describe a durable pair of hiking boots), fragility (e.g., category “brittle”), and the like.

In some examples, the systems and methods described herein may operate using the taxonomy defined herein. For example, the system may determine whether there is enough DDO performance data to satisfy a threshold for a particular promotion. If not, the system will determine whether there is enough DDO performance data to satisfy a threshold for “Jewelry—Gold”, if not, as described at least with respect to FIG. 5, the system will advantageously, in some examples, proceed to the next tier, in this case “Jewelry” to determine whether a threshold has been satisfied. In cases where the category “Jewelry” satisfies the threshold number of impressions, the system will assign or otherwise use the categories DDO performance data as a proxy for the sub category or promotions data that did not satisfy the threshold.

FIG. 7 shows a schematic block diagram of circuitry 700, some or all of which may be included in, for example, recommendation engine 115. As illustrated in FIG. 7, in accordance with some example embodiments, circuitry 700 can include various means, such as processor 702, memory 704, communications module 706, and/or input/output module 708. As referred to herein, “module” includes hardware, software and/or firmware configured to perform one or more particular functions. In this regard, the means of circuitry 700 as described herein may be embodied as, for example, circuitry, hardware elements (e.g., a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising computer-readable program instructions stored on a non-transitory computer-readable medium (e.g., memory 704) that is executable by a suitably configured processing device (e.g., processor 702), or some combination thereof.

Processor 702 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in FIG. 7 as a single processor, in some embodiments, processor 702 comprises a plurality of processors. The plurality of processors may be embodied on a single computing device or may be distributed across a plurality of computing devices collectively configured to function as circuitry 700. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of circuitry 700 as described herein. In an example embodiment, processor 702 is configured to execute instructions stored in memory 704 or otherwise accessible to processor 702. These instructions, when executed by processor 702, may cause circuitry 700 to perform one or more of the functionalities of circuitry 700 as described herein.

Whether configured by hardware, firmware/software methods, or by a combination thereof, processor 702 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when processor 702 is embodied as an ASIC, FPGA or the like, processor 702 may comprise specifically configured hardware for conducting one or more operations described herein. Alternatively, as another example, when processor 702 is embodied as an executor of instructions, such as may be stored in memory 704, the instructions may specifically configure processor 702 to perform one or more algorithms and operations described herein, such as those discussed in connection with FIG. 1.

Memory 704 may comprise, for example, volatile memory, non-volatile memory, or some combination thereof. Although illustrated in FIG. 7 as a single memory, memory 704 may comprise a plurality of memory components. The plurality of memory components may be embodied on a single computing device or distributed across a plurality of computing devices. In various embodiments, memory 704 may comprise, for example, a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD-ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof. Memory 704 may be configured to store information, data (including analytics data), applications, instructions, or the like for enabling circuitry 700 to carry out various functions in accordance with example embodiments of the present invention. For example, in at least some embodiments, memory 704 is configured to buffer input data for processing by processor 702. Additionally or alternatively, in at least some embodiments, memory 704 is configured to store program instructions for execution by processor 702. Memory 704 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by circuitry 700 during the course of performing its functionalities.

Communications module 706 may be embodied as any device or means embodied in circuitry, hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., memory 704) and executed by a processing device (e.g., processor 702), or a combination thereof that is configured to receive and/or transmit data from/to another device, such as, for example, a second circuitry 700 and/or the like. In some embodiments, communications module 706 (like other components discussed herein) can be at least partially embodied as or otherwise controlled by processor 702. In this regard, communications module 706 may be in communication with processor 702, such as via a bus. Communications module 706 may include, for example, an antenna, a transmitter, a receiver, a transceiver, network interface card and/or supporting hardware and/or firmware/software for enabling communications with another computing device. Communications module 706 may be configured to receive and/or transmit any data that may be stored by memory 704 using any protocol that may be used for communications between computing devices. Communications module 706 may additionally or alternatively be in communication with the memory 704, input/output module 708 and/or any other component of circuitry 700, such as via a bus.

Input/output module 708 may be in communication with processor 702 to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. Some example visual outputs that may be provided to a user by circuitry 700 are discussed in connection with FIG. 1. As such, input/output module 708 may include support, for example, for a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, a RFID reader, barcode reader, biometric scanner, and/or other input/output mechanisms. In embodiments wherein circuitry 700 is embodied as a server or database, aspects of input/output module 708 may be reduced as compared to embodiments where circuitry 700 is implemented as an end-user machine or other type of device designed for complex user interactions. In some embodiments (like other components discussed herein), input/output module 708 may even be eliminated from circuitry 700. Alternatively, such as in embodiments wherein circuitry 700 is embodied as a server or database, at least some aspects of input/output module 708 may be embodied on an apparatus used by a user that is in communication with circuitry 700. Input/output module 708 may be in communication with the memory 704, communications module 706, and/or any other component(s), such as via a bus. Although more than one input/output module and/or other component can be included in circuitry 700, only one is shown in FIG. 7 to avoid overcomplicating the drawing (like the other components discussed herein).

Predictive recommendation engine module 710 may also or instead be included and configured to perform the functionality discussed herein related to the recommendation engine discussed above. In some embodiments, some or all of the functionality of predictive recommendation engine may be performed by processor 702. In this regard, the example processes and algorithms discussed herein can be performed by at least one processor 702 and/or predictive recommendation engine module 710. For example, non-transitory computer readable media can be configured to store firmware, one or more application programs, and/or other software, which include instructions and other computer-readable program code portions that can be executed to control each processor (e.g., processor 702 and/or predictive recommendation engine module 710) of the components of system 100 to implement various operations, including the examples shown above. As such, a series of computer-readable program code portions are embodied in one or more computer program products and can be used, with a computing device, server, and/or other programmable apparatus, to produce machine-implemented processes.

As described above in this disclosure, aspects of embodiments of the present invention may be configured as methods, mobile devices, backend network devices, and the like. Accordingly, embodiments may comprise various means including entirely of hardware or any combination of software and hardware. Furthermore, embodiments may take the form of a computer program product on at least one non-transitory computer-readable storage medium having computer-readable program instructions (e.g., computer software) embodied in the storage medium. Any suitable computer-readable storage medium may be utilized including non-transitory hard disks, CD-ROMs, flash memory, optical storage devices, or magnetic storage devices.

Embodiments of the present invention have been described above with reference to block diagrams and flowchart illustrations of methods, apparatuses, systems and computer program products. It will be understood that each block of the circuit diagrams and process flow diagrams, and combinations of blocks in the circuit diagrams and process flowcharts, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus, such as processor 702 and/or predictive recommendation engine module 710 discussed above with reference to FIG. 7, to produce a machine, such that the computer program product includes the instructions which execute on the computer or other programmable data processing apparatus create a means for implementing the functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computer-readable storage device (e.g., memory 704) that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage device produce an article of manufacture including computer-readable instructions for implementing the function discussed herein. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions discussed herein.

Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the circuit diagrams and process flowcharts, and combinations of blocks in the circuit diagrams and process flowcharts, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. 

What is claimed is:
 1. A system for generating a combined feature for selecting a device rendered object to be transmitted to a network asset requester device, the system comprising a least one processor and at least one memory including computer program code, the at least one memory and the computer code configured to, with the at least one processor, cause the system to: receive DDO feature data representing the device rendered object, wherein the DDO feature data include data collected from a first set of impressions associated with a device rendered object permalink; determine whether the first set of impressions satisfies a threshold quantity of impressions; and in an instance in which the first set of impressions does not satisfy the threshold quantity, generate tiered DDO feature data representing the device rendered object, wherein the tiered DDO feature data were collected from a second set of impressions representing a tier group of device rendered objects including the device rendered object; generate historical feature data based on a predicted gender type associated with first name data received from the network asset requester device, wherein the historical feature data representing the tier group of device rendered objects related to the predicted gender type; integrate the tiered DDO feature data and the historical feature data; generate the combined feature using the historical feature data and one of the DDO feature data or the integrated tiered DDO feature data; select, based on the combined feature, a subset of promotions from a plurality of promotions, the subset of promotions to be recommended to a customer; and transmit the subset of promotions to a client device associated with the customer for display via the client device.
 2. The system of claim 1, further caused to: retrieve known gender data from one or more user profiles associated with the first name data; calculate one or more gender ratios that are each correlated to respective gender types based on the known gender data retrieved from the one or more user profiles; compare each of the one or more gender ratios with a threshold ratio; in an instance in which a gender ratio is equal to or greater than the threshold ratio, determine the predicted gender type to be a gender type correlated to the gender ratio; and in an instance in which a gender ratio is smaller than the threshold ratio, determine the predicted gender type to be an unknown type.
 3. The system of claim 2, wherein the gender type is a male type, or a female type.
 4. The system of claim 2, wherein the threshold ratio is 0.85.
 5. The system of claim 1, wherein the predicted gender type is generated using a machine learning model.
 6. The system of claim 1, further caused to: generate the combined feature using the historical feature data and the DDO feature data in an instance in which the first set of impressions satisfies the threshold quantity of impressions.
 7. The system of claim 1, wherein the historical feature data represents a tier of device rendered objects related to the predicted gender type.
 8. The system of claim 1, further caused to: select device rendered objects to be transmitted to the network asset requester device based on the combined feature.
 9. The system of claim 1, further caused to: integrate historical behavior data collected from a sample of network asset requester devices and recently collected behavior data to generate DDO feature data.
 10. The system of claim 7, further caused to: generate the historical feature data based on one or more detected historical trends.
 11. The system of claim 8, wherein selecting device rendered objects to be transmitted to the network asset requester device based on the combined feature comprises: receiving input data representing a request from the network asset requester device; receiving user profile describing attributes of the network asset requester device; receiving, from a device rendered object inventory, device rendered object data describing attributes of a set of available device rendered object for the network asset requester device; calculating, based on at least one relevance model, a contextual relevance score for each of the set of device rendered object using the input data, the device rendered object data, and the user profile; and ranking the set of available device rendered object based on their respective contextual relevance scores.
 12. An apparatus, operable on a distributed computing system, to generate a combined feature for selecting a device rendered object to be transmitted to a network asset requester device, the apparatus comprising: a relevance engine, wherein the relevance engine comprises an input/output module and the relevance engine is stored in a memory such that when executed by a processor the relevance engine is configured to receive, via the input/output module, one or more network asset requests and output one or more ranked available promotions in response to the network asset request, the ranked available device rendered objects generated in part by at least a predictive model builder and a DDO feature data integrator; wherein the relevance engine is further configured to receive first name data from the network asset requester device; wherein the predictive model builder is stored in the memory such that when executed by the processor the predictive model builder is configured to integrate DDO feature data, received via a network interface representing a device rendered object permalink, and historical feature data generated based on a predicted gender type associated with the first name data, the historical feature data representing the tier group of device rendered objects related to the predicted gender type, wherein the DDO feature data include data collected from a first set of impressions associated with the device rendered object permalink; wherein the DDO feature data integrator is stored in the memory such that when executed by the processor the DDO feature data integrator is configured to determine that the first set of impressions satisfies a threshold quantity of impressions and to generate a combined feature using the integrated DDO feature data and the historical feature data; and wherein the relevance engine is configured to select, based on the combined feature, a subset of promotions from a plurality of promotions, the subset of promotions to be recommended to a customer; and a communications module configured to transmit the subset of promotions to a client device associated with the customer for display via the client device.
 13. The apparatus of claim 12, wherein the DDO feature data integrator is further configured to determine that the first set of impressions does not satisfy the threshold quantity of impressions.
 14. The apparatus of claim 13, wherein the predictive model builder is further configured to: generate tiered DDO feature data representing the device rendered object, wherein the tiered DDO feature data were collected from a second set of impressions representing a tier group of device rendered objects including the device rendered object, integrate the tiered DDO feature data and the historical feature data, and generate a combined feature using the integrated tiered DDO feature data and the historical feature data.
 15. The apparatus of claim 12, wherein the predictive model builder is further configured to integrate historical behavior data collected from a sample of network asset requester devices and recently collected behavior data to generate the DDO feature data.
 16. The apparatus of claim 12, wherein the predictive model builder is further configured to: retrieve, from the memory, known gender data from one or more user profiles associated with the first name data; calculate, using the processor, one or more gender ratios that are each correlated to respective gender types based on the known gender data retrieved from the one or more user profiles associated with the first name data; compare, using the processor, each of the one or more gender ratios that are each correlated to the respective gender types with a threshold ratio; and in an instance in which a gender ratio is larger than or equal to the threshold ratio, determine, using the processor, the predicted gender type to be a gender type correlated to the gender ratio; and in an instance in which a gender ratio is smaller than the threshold ratio, determine, using the processor, the predicted gender type to be an unknown type.
 17. The apparatus of claim 16, wherein the gender type is a male type, or a female type.
 18. The apparatus of claim 16, wherein the threshold ratio is 0.85.
 19. The apparatus of claim 12, wherein the predicted gender type is generated using machine learning.
 20. The apparatus of claim 12, wherein the predictive model builder is further configured to generate the historical feature data based on one or more detected historical trends derived from one or more historical databases.
 21. The apparatus of claim 12, wherein the relevance engine is further configured to select device rendered objects to be recommended to a network asset requester device based on the combined feature.
 22. The apparatus of claim 21, wherein selecting device rendered objects to be transmitted to the network asset requester device based on the combined feature comprises: receiving input data representing a request from the network asset requester device; receiving user profile describing attributes of the network asset requester device; receiving, from a device rendered object inventory, device rendered object data describing attributes of a set of available device rendered object for the network asset requester device; calculating, based on at least one relevance model, a contextual relevance score for each of the set of device rendered objects using the input data, the device rendered object data, and the user profile; and ranking the set of available device rendered objects based on their respective contextual relevance scores. 